<html>
<head><meta charset="utf-8"><title>stdlib and target stability questions · t-libs · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/index.html">t-libs</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html">stdlib and target stability questions</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="229916904"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229916904" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229916904">(Mar 11 2021 at 20:07)</a>:</h4>
<p>Hello,</p>
<p><code>wasm32-wasi</code> is currently  in stable rust. However, unlike almost all other rust targets, this is far from stable with both the bytecode evolving and the stdlib capabilities. For example it has moved wasi namespace name from <code>unstable-.....</code> to <code>preview....</code>. Also the current name <code>preview</code> hints that this is not really something stable, yet it is in stable rust.</p>
<p>In WASM-related circles, <a href="https://github.com/WebAssembly/tool-conventions/issues/158">https://github.com/WebAssembly/tool-conventions/issues/158</a> there are proposals that tie WASM to browser evolutions. </p>
<p>This is hurting IOT-like scenarios (where host VMs cannot evolve at the same pace) a lot, as users of rust in these situations are forced to sit on a rust version for longer than needed, just because <code>wasm32-wasi</code> changes at an unpredictable pace. Right now it's a die roll if it works after a rustc update.</p>
<p>And this brings me to the topic:<br>
1) What stability guarantees should rust have for it's targets?<br>
2) Could we add flags similar to CPU feature flags that enable extra stdlib features. in a similar way to <code>+avx...</code> e.g. <code>+threads</code> for the wasi features?<br>
3) If there are no written down stability guidelines for rustc targets where can we discuss some? <br>
4) Is there a proposal somewhere that can allow an older stdlib to be used with a newer rust? I couldn't find such a thing but that would mitigate some of the pain, as we can pin the stdlib version while still getting language features.</p>



<a name="229917440"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229917440" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> simulacrum <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229917440">(Mar 11 2021 at 20:10)</a>:</h4>
<p>That room should exist -- not sure why you're not seeing it, maybe you need to subscribe to it. I can move this to there, and that should get you a link.</p>



<a name="229917476"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229917476" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Notification Bot <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229917476">(Mar 11 2021 at 20:10)</a>:</h4>
<p>This topic was moved here from <a class="stream-topic" data-stream-id="196563" href="/#narrow/stream/196563-t-lang.2Fmeta/topic/stdlib.20and.20target.20stability.20questions">#t-lang/meta &gt; stdlib and target stability questions</a> by <span class="user-mention silent" data-user-id="116122">simulacrum</span></p>



<a name="229919159"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229919159" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229919159">(Mar 11 2021 at 20:20)</a>:</h4>
<p>As i discussed in another topic, Moving wasm32-wasi to nightly only won't really fix the issue, but I wonder what is the way that we can improve this situation since right now it seems really inconsistent and unpredictable. </p>
<p>Thinking about it, maybe my question is not for #t-libs only but meta?</p>



<a name="229919604"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229919604" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Amanieu <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229919604">(Mar 11 2021 at 20:23)</a>:</h4>
<p>cc <span class="user-mention" data-user-id="116015">@Alex Crichton</span> since this issue has come up before in the context of <code>stdarch</code>.</p>



<a name="229920716"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229920716" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229920716">(Mar 11 2021 at 20:31)</a>:</h4>
<p>For (1), general stability rustc should have for its targets, that's an extremely broad question and I won't get into it much myself. My belief is that stability should be defined within targets, so stability for x86_64-unknown-linux-gnu is not the same thing as wasm32-wasi. I would assert that this is required, because you wouldn't see a wasm32-wasi target in rustc for decades.</p>



<a name="229920784"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229920784" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229920784">(Mar 11 2021 at 20:31)</a>:</h4>
<p>Another thing that could help here would be a custom stdlib with a newer rustc would also help. Worst case scenario maybe IOT-like scenarios would fork stdlib, rename it, use <code>#nostd</code> then use it as a normal crate dependency but this is a convoluted solution that we can probably help make better</p>



<a name="229920792"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229920792" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229920792">(Mar 11 2021 at 20:31)</a>:</h4>
<p>For (2) this already exists today, we inherit features from LLVM so you can do things like <code>-Ctarget-features=+simd128</code> and similar for some other implemented proposals in wasm. The names aren't super great since we inherit them raw from LLVM, however</p>



<a name="229920857"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229920857" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229920857">(Mar 11 2021 at 20:32)</a>:</h4>
<p>For (3) I don't believe there are stability guidelines written down for wasm</p>



<a name="229920902"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229920902" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229920902">(Mar 11 2021 at 20:32)</a>:</h4>
<p>For (4) I don't believe there is such a proposal, and I doubt it would ever be accepted personally</p>



<a name="229921016"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229921016" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229921016">(Mar 11 2021 at 20:33)</a>:</h4>
<p>But should we have some minimal guarantees on stable targets?</p>



<a name="229921026"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229921026" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229921026">(Mar 11 2021 at 20:33)</a>:</h4>
<p>My general thoughts on this is that if you're hitting tons of breaking with changes in wasi that's a problem we should fix. I don't think it needs a grand rethinking of all targets in Rust per-se, it may be that WASI just isn't doing the right thing</p>



<a name="229921073"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229921073" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229921073">(Mar 11 2021 at 20:33)</a>:</h4>
<p>I would be fine to talk about specific breakages, but if you want to talk more generally I'm not really in a position to continue that conversation, it's not my wheelhouse</p>



<a name="229921223"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229921223" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229921223">(Mar 11 2021 at 20:34)</a>:</h4>
<p>I think WASI in particular is the culprit, as WASM generally treats is as a CPU feature mostly so that's a bit better, even if the pace is kind of not sustainable for certain kind of scenarios, that's easier to fix, but WASI in particular is unclear where I can discuss that</p>



<a name="229921508"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229921508" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229921508">(Mar 11 2021 at 20:36)</a>:</h4>
<p>If you'd like to talk about specific breakages you've seen on WASI I can help out with that, if you want to talk about the general stability of the WASI target I don't know what to do about that. AFAIK there's not really someone or some team or other in charge of that. It just sort of is what it is now and folks contributing and reviewing WASI changes do a best-effort thing to hopefully ensure no one unreasonably gets broken</p>



<a name="229922150"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229922150" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229922150">(Mar 11 2021 at 20:41)</a>:</h4>
<p>Is it the WASI standardisation team that usually does changes here? Is it coming from somewhere else? It's unclear how i can start helping to be honest, most meetings online are either standardisation related (mostly about WASM, not wasi), but that's a different beast from the implementation.</p>



<a name="229922400"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229922400" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229922400">(Mar 11 2021 at 20:42)</a>:</h4>
<p>I have some trouble understanding how the pipeline works of getting wasi features / changes into rustc stdlib and how that's supposed to evolve along with the standard (especially since the standard isn't really done) :D</p>



<a name="229922429"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229922429" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229922429">(Mar 11 2021 at 20:42)</a>:</h4>
<p>Yeah most wasi things have been me/sunfish. I should also point out that my thoughts here are all very wasm32-wasi specific, and so if you'd like to talk more broadly I just don't have much to offer myself, but I don't want to shut down anyone else's thoughts.</p>



<a name="229922493"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229922493" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229922493">(Mar 11 2021 at 20:43)</a>:</h4>
<p>Currently the way things work are that when the standard changes we update rust. That's happened only once, though, so it's not like there's much of a trend here</p>



<a name="229922670"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229922670" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229922670">(Mar 11 2021 at 20:44)</a>:</h4>
<p>That's ok my use case is wasm32-wasi. I did see thread mentioned as something in the pipeline but in that case it's ok (as threads panic now so it's not really a regression). The part that's worrying me for example is memory operations since those work now in a slow way (e.g. memcpy-equivalent), but if we add intrinsics in wasi for that, then it will break usable programs. today that run on VMs that don't have those exposed</p>



<a name="229922803"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229922803" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229922803">(Mar 11 2021 at 20:45)</a>:</h4>
<p>I'm not sure how to address hypothetical breakage. No one's proposed turning on bulk-memory-operations by default yet.</p>



<a name="229922825"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229922825" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229922825">(Mar 11 2021 at 20:45)</a>:</h4>
<p>Also AFAIK no one's proposaing adding intrinsics to wasi for this</p>



<a name="229923190"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229923190" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229923190">(Mar 11 2021 at 20:48)</a>:</h4>
<p>So the worry here is that's unclear how it will be turned on and where these things are usually discussed.</p>



<a name="229923819"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229923819" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229923819">(Mar 11 2021 at 20:53)</a>:</h4>
<p>AFAIK there's no precedent for this</p>



<a name="229923832"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229923832" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229923832">(Mar 11 2021 at 20:53)</a>:</h4>
<p>nothing major has been stabilized in the past and has been enticing enough to use</p>



<a name="229923844"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229923844" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229923844">(Mar 11 2021 at 20:53)</a>:</h4>
<p>so... whatever happens next is entirely unknown</p>



<a name="229923972"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229923972" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229923972">(Mar 11 2021 at 20:54)</a>:</h4>
<p>no one has proposed making these changes, and this style of change has not happened in the past, so... all I can really recommend is to try to follow development and if it pops up and causes problems then we can try to fix</p>



<a name="229923979"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229923979" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229923979">(Mar 11 2021 at 20:54)</a>:</h4>
<p>the goal is to not break everyone...</p>



<a name="229924045"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229924045" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229924045">(Mar 11 2021 at 20:54)</a>:</h4>
<p>when env changed for wasi functions from the previous name of <code>unstable-</code> to <code>preview-</code> is something that popped to mind that altered results while VMs (e.g. WAMR required changes to update those namespaces)</p>



<a name="229924232"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229924232" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229924232">(Mar 11 2021 at 20:56)</a>:</h4>
<p>I guess I anticipate these things to appear as people work through them: e.g. this is the only discussion i found on how to enable WASM features (not wasi). <a href="https://github.com/WebAssembly/tool-conventions/issues/158">https://github.com/WebAssembly/tool-conventions/issues/158</a></p>



<a name="229924441"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229924441" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229924441">(Mar 11 2021 at 20:57)</a>:</h4>
<p>So when you say monitor development, what is the group you're referring to specifically? is the WebAssembly one mentioned above the place where defaults are decided or is it decided here for wasi (or both :D)?</p>



<a name="229924813"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229924813" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229924813">(Mar 11 2021 at 21:00)</a>:</h4>
<p>My best advice is the rust repository itself and changes to wasi's implementation of libstdt</p>



<a name="229924867"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/229924867" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#229924867">(Mar 11 2021 at 21:00)</a>:</h4>
<p>Alright, thanks for the help.</p>



<a name="230030266"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/stdlib%20and%20target%20stability%20questions/near/230030266" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alexandru Ene <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/stdlib.20and.20target.20stability.20questions.html#230030266">(Mar 12 2021 at 13:45)</a>:</h4>
<p>By the way, for future readers of this thread, i realized that I was wrong on how to think about stable rust versions and targets available in stable rust and stdlibs versions in stable rust to support those targets. Targets are more like platforms that have tiers and those tiers come with some level of guarantees already.</p>
<p>The contribution I see valuable moving forward that I could make for things breaking use-cases once features move into the default set is to contribute flags to disable those features whenever necessary. That way people get things by default and IOT-lile use-cases aren't stuck on a compiler version.</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>